Skip to content

Conversation

jwrct
Copy link
Contributor

@jwrct jwrct commented Jul 9, 2025

What does this PR do?
Closes #5989
Why are these changes required?

This PR has been tested by:

  • Unit Tests
  • Manual Testing

Follow up

Extra details

@kuny0707 kuny0707 moved this to In Review in java-tron Jul 9, 2025
@jwrct jwrct changed the base branch from develop to release_v4.8.1 July 9, 2025 03:58
@jwrct jwrct changed the title fix(net): fix for ambiguous reason code in disconnect messages fix(net): fix the unclear reason codes returned in disconnection messages Jul 9, 2025
@@ -126,13 +126,27 @@ public void testInvalidHelloMessage() {
//block hash is empty
try {
BlockCapsule.BlockId hid = ChainBaseManager.getChainBaseManager().getHeadBlockId();
Protocol.HelloMessage.BlockId hBlockId = Protocol.HelloMessage.BlockId.newBuilder()
.setHash(ByteString.copyFrom(new byte[0]))
Protocol.HelloMessage.BlockId okBlockId = Protocol.HelloMessage.BlockId.newBuilder()
Copy link
Contributor

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

what about using "validBLockId" instead of "okBlockId"?

Copy link
Contributor Author

Choose a reason for hiding this comment

The reason will be displayed to describe this comment to others. Learn more.

Test case adjustment only.

@kuny0707 kuny0707 merged commit 6c29cb2 into tronprotocol:release_v4.8.1 Aug 13, 2025
8 checks passed
@github-project-automation github-project-automation bot moved this from In Review to Done in java-tron Aug 13, 2025
Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment
Labels
None yet
Projects
Status: Done
Development

Successfully merging this pull request may close these issues.

Ambiguous Reason Code in Disconnection Message
9 participants